System, method, and computer-readable medium for schedule-based telecommunication policies

ABSTRACT

A system, method and computer-readable medium for enforcing user telecommunication privileges on a per-schedule basis are provided. Enterprise members may have a schedule associated therewith that defines scheduled locations of the users. Telecommunication service privileges may be coordinated with the users&#39; schedules such that communication services are disabled at particular times based on the users&#39; schedules. In other implementations, particular users may have telecommunication services disabled by an administrator in the event of a catastrophe or emergency. By this mechanism, users that are not proximate to a particular catastrophe or emergency area according to the users&#39; schedule may have services disabled while other users that are located more proximate to the emergency may have their telecommunication services enabled. In this manner, the demand on a cellular network may be alleviated thereby increasing the likelihood that users directly impacted by the emergency may receive and place calls or access data services.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims priority of and is a continuation of U.S. Ser.No. 14/659,226 entitled “SYSTEM, METHOD, AND COMPUTER-READABLE MEDIUMFOR SCHEDULE-BASED TELECOMMUNICATION POLICIES” filed Mar. 16, 2015,issued U.S. Pat. No. 9,215,728, issued Dec. 15, 2015, which is acontinuation of U.S. Ser. No. 11/942,568, entitled “SYSTEM, METHOD, ANDCOMPUTER-READABLE MEDIUM FOR SCHEDULE-BASED TELECOMMUNICATION POLICIES”filed Nov. 19, 2007, issued U.S. Pat. No. 8,983,506, issued Mar. 17,2015, which is incorporated herein by reference for all purposes.

FIELD OF THE INVENTION

The present disclosure relates to telecommunications and, moreparticularly, to enforcing user privileges in a telecommunicationssystem according to a schedule-based policy.

BACKGROUND

Cellular service has conventionally been controlled by wireless carriernetworks and managed independently of, and with no connectivity to,enterprise voice and data networks. Enterprises today control theirenterprise fixed voice and data networks by deployment of private branchexchanges (PBXs). The enterprise may own and manage PBXs within eachbranch and between branch offices. The enterprise may also manage theirown data networks and corporate local area network (LAN)/wide areanetwork (WAN). Bulk voice minutes and data capacity may be purchasedfrom land-line carriers, or from other providers that have purchasedbulk minutes and data capacity from carriers. The purchased capacity maythen be used to connect branch offices using public IP Networkproviders, e.g., MCI, Sprint, L3, etc., for Data and Voice over IP(VoIP).

A premise with numerous members or users may have various facilities.The use of cellular communication devices on such premises is oftenprohibited or discouraged. For example, some schools have bannedcellular telephone usage due to class interruptions and/or studentscheating during exams by accessing the Internet on their mobile phones,text messaging other students for exam answers, or by other mechanisms.However, there are many cases when it may be desirable for students orfaculty to be equipped with cellular telephone service, e.g., in thecase of a natural disaster, a campus emergency, or other distress. Forexample, numerous school shootings have been well documented in theUnited States. In such situations, law enforcement may be greatly aidedby receiving reports from students or faculty regarding an assailant orother information regarding an in-progress crime. Because such cases arehigh profile and quickly reported by various media, cellular systemsoften become overwhelmed due to students and family members placingcalls to other students or family members. The high number of callsplaced during such an event can quickly consume the cellular systemcapacity to the point where calls are unable to be placed to or from acellular customer in a service area corresponding to the emergency.

Heretofore, no mechanisms have been provided to alleviate the abovedisadvantages.

SUMMARY OF THE INVENTION

Embodiments disclosed herein provide mechanisms for enforcing usertelecommunication privileges on a schedule basis. Using mechanismsdescribed herein, users of an enterprise or other campus or entity mayhave a schedule associated therewith that defines scheduled locations ofthe users. Telecommunication service privileges may be coordinated withthe users' schedules such that certain services are disabled atparticular times based on the users' schedules. In otherimplementations, particular users may have telecommunication servicesdisabled by an administrator, e.g., in the event of a catastrophe oremergency. By this mechanism, users that are not proximate to aparticular catastrophe or emergency area according to the users'schedules may have services disabled while other users that are locatedmore proximate to the emergency may have their telecommunicationservices enabled. In this manner, the demand on a cellular network maybe alleviated thereby increasing the likelihood that users directlyimpacted by the emergency may receive and place calls or access dataservices.

BRIEF DESCRIPTION OF THE DRAWINGS

Aspects of the present disclosure are best understood from the followingdetailed description when read with the accompanying figures, in which:

FIG. 1 is a diagrammatic representation of a network architecture inwhich embodiments disclosed herein may be implemented;

FIG. 2 is a diagrammatic representation of an embodiment of carriergateway server depicted in FIG. 1;

FIG. 3 is a diagrammatic representation of enterprise facility in whichschedule-based telecommunication policies may be enforced in accordancewith an embodiment;

FIG. 4 diagrammatic representation of an embodiment of a scheduledatabase configured for enterprise member schedules;

FIG. 5 is a flowchart depicting a schedule-based communications policyenforcement routine implemented in accordance with an embodiment;

FIG. 6 is a flowchart depicting processing of a schedule andlocation-based communications policy enforcement routine for restrictingcommunication service privileges based on a member schedule andlocation;

FIG. 7 is a flowchart depicting a schedule-based communications policyenforcement routine that facilitates service restriction exemptionsimplemented in accordance with an embodiment;

FIG. 8 is flowchart depicting a schedule-based communications policyenforcement routine including emergency service restriction suspensionimplemented in accordance with an embodiment; and

FIG. 9 is a flowchart depicting a location evaluation subroutineimplemented in accordance with an embodiment.

DETAILED DESCRIPTION

It is to be understood that the following disclosure provides manydifferent embodiments, or examples, for implementing different featuresof various embodiments. Specific examples of components and arrangementsare described below to simplify the present disclosure. These are, ofcourse, merely examples and are not intended to be limiting. Inaddition, the present disclosure may repeat reference numerals and/orletters in the various examples. This repetition is for the purpose ofsimplicity and clarity and does not in itself dictate a relationshipbetween the various embodiments and/or configurations discussed.

With the ubiquity of cellular communication devices, it is desirable toseamlessly integrate public wireless voice and data networks withenterprise networks. More particularly, it is desirable to provideenterprise cellular solutions that may operate in conjunction withpublic network infrastructure. As referred to herein, an enterprise maycomprise a corporation, an education facility, or any other entity thatmay have infrastructure to which a plurality of cellulartelecommunication users may have access. As referred to herein, a memberrefers to a user of the enterprise infrastructure. For example, in theevent that the enterprise is implemented as a corporation, a member mayrefer to an employee of the enterprise. Similarly, in the event that theenterprise is implemented as an education facility such as a university,a member may refer to a student or faculty of the university.

In accordance with the present disclosure, the enterprise may maintain aschedule that defines times and locations, e.g., a particular buildingand office or room of the building, where members are scheduled to belocated. A gateway server inter-connects a carrier network's MobileSwitching Center (MSC) that manages cellular voice traffic as well asthe carrier's Serving GPRS Support Node (SGSN) that manages cellulardata traffic, with the enterprise's voice and data network. Inaccordance with a particular embodiment, a carrier gateway server (GS-C)deployed in a cellular network is interconnected with an enterprisegateway server (GS-E). Within the enterprise network, a member scheduleis maintained and may be interfaced with the GS-E. Service Policies maybe enforced by the GS-E according to the schedule. Further, a systemadministrator may disable, e.g., in the case of an emergency, certaintelecommunication services for particular members according to members'scheduled locations while other members' telecommunication services areenabled based on those members' locations.

FIG. 1 is a diagrammatic representation of a network architecture inwhich embodiments disclosed herein may be implemented. Network 100 mayinclude a cellular network system 110, such as a Global System forMobile (GSM) Communications network, a code division multiple access(CDMA) network, a mobile network utilizing IMT-2000, or another suitablemobile network. Cellular network system 110 generally includes aSwitching System (SS) 120 and a Base Station System (BSS) 130. In theexamples provided herein, mobile network architecture components aremade with reference to the GSM, the most popular standard for mobilephones in the world. GSM is both an air interface and networkingprotocol. The most popular alternative combines the Code DivisionMultiple Access (CDMA) air interface protocol and the ANSI-41 networkingprotocol.

Each of SS 120 and BSS 130 contain a number of functional units wellunderstood by those skilled in the art, and a detailed explanation ofthe various components is unnecessary. Nevertheless, a cursory review ofvarious components is provided. SS 120 contains a Mobile servicesSwitching Center (MSC) 122, a Home Location Register (HLR) 124, and aVisitor Location Register (VLR) 126. MSCs carry out switching functionsand manage the communications between mobile phones and the PublicSwitched Telephone Network (PSTN) 190. HLR 124 comprises the centraldatabase that contains details of each mobile phone subscriber that isauthorized to use the cellular core network. VLR 126 comprises adatabase which stores information about all the mobiles terminals thatare currently serviced by the associated MSC (MSC 122 in the presentexample). VLR 126 stores various information regarding the mobileterminals, such as the current location area identity that specifies aparticular base station controller (BSC) that the mobile station iscurrently serviced by.

Various other sub-systems or functional modules may, and typically are,included in SS 120, such as an Authentication Center, an EquipmentIdentity Register, or various other functions. A serving general packetradio service (GPRS) support node (SGSN) 128 may be included in cellularnetwork system 110 to facilitate provisioning of packet services to andfrom mobile terminals in network system 110. GPRS provides mobilitymanagement, session management and transport for Internet Protocolpacket services in GSM cellular packet networks.

As is understood, various GPRS infrastructure may be included in networksystem 110 to provide packet services to mobile terminals, and only SGSN128 of the GPRS core network is depicted to simplify the discussion ofembodiments disclosed herein. In general, a gateway GPRS support nodemay interface the GPRS backbone with an external packet network, such asthe Internet.

SGSN 128 may interface with various subsystems of network system 110.For example, SGSN 128 may have a Gs interface with MSC 122 and VLR 126that facilitates paging and station availability notification whenperforming data transfers. SGSN 128 may additionally have a Gr interfacewith HLR 124 through which messaging may be performed, for example, overthe Mobile Application Part protocol. SGSN 128 may additionally have aGb interface with packet control unit (PCU) (not shown) of BSS 130 thatfacilitates connection of BSS 130 with SGSN 128.

Network system 110 may also include a signaling system, such as a SS7network 160. SS7 network 160 provides a set of telephony signalingprotocols which are used to set up the vast majority of the world's PSTNtelephone calls. SS7 network 160 is also used in cellular networks, suchas GSM and UMTS, for circuit switched voice and packet-switched dataapplications. As is understood, SS7 network 160 includes varioussignaling nodes, such as any number of service control points (SCPs)162, signal transfer points (STPs) 164, and service switching points(SSPs) 166.

BSS 130 contains a Base Station Controller (BSC) 132 that may be incommunication with and in control of a plurality of Base TransceiverStations (BTSs) 134-138. Each individual BTS 134-138 under the controlof a given BSC 132 may define a radio cell operating on a set of radiochannels thereby providing service to a Mobile Terminal.

Network system 110 may also include a Mobile Location Center (MLC) 146that may communicate with a plurality of Mobile Switching Centers (MSCs)122 and Base Station Controllers (BSCs) 132 for the purpose of obtaininghighly granular location information of a mobile telephone such as MT140-142.

Network system 110 may also include a short message service center(SMSC) 144 adapted to deliver short message service (SMS) messages tomobile terminals. When an SMS message is sent to a user, the SMS messageis stored in SMSC 144 which delivers it to the destination mobileterminal when the destination mobile terminal is available. As is known,the SMS message may be delivered via a control channel, e.g., a cellbroadcast control channel, or bearer channel.

Network 100 may include an enterprise network 150, such as a switchedEthernet, that interconnects various network nodes via various networkinfrastructure, such as hubs and switches. Enterprise network 150 mayinclude various client nodes, such as desktop clients, land-lineInternet Protocol (IP) telephones 154-155, and an IP private branchexchange (PBX) 158 which carries calls over IP, e.g., via voice over IP(VoIP). Enterprise network 150 may interface with the PSTN 190 via arouter 172 disposed at the enterprise.

Likewise, enterprise network 150 may interface with cellular networksystem 110 via routers 170 and 172. It is understood that enterprisenetwork 150 may, and typically does, include hundreds or thousands ofclient devices and networking nodes, and the architecture depicted inFIG. 1 is greatly simplified to facilitate a discussion of embodimentsdisclosed herein.

In accordance with an embodiment, an enterprise gateway server (GS-E)182 may be deployed in enterprise network 150 that is adapted tointer-connect the mobile network's MSC 122 that manages cellular voicetraffic as well as the SGSN 128 that manages cellular data traffic. Tothis end, GS-E 182 may interface with a carrier gateway server (GS-C)180. The network may also include a softswitch media gateway 181. Froman IT organization perspective, GS-C 180 appears as an extension to PBX158. To cellular network system 110, GS-C 180 appears as a standardin-network endpoint for delivering calls. To PBX 158, GS-C 180 appearsas a set of standard PBX endpoints (e.g. deskphones, or IP clients).GS-C 180 mediates between the two disparate sets of network protocolsand state machines.

GS-C 180 may include the network functions for both voice (gateway MSC)and data (gateway GPRS Support Node or Home Agent), VoIP capability forinterconnecting mobile network 110 with enterprise network 150 therebyeliminating PSTN interconnect charges, a billing gateway, and anext-generation Network Services gateway that enables third party valueadded services for the enterprise, such as mobile phoneactivation/de-activation, corporate directory integration based on IMS(IP Multimedia Subsystem), or other services. Gateway server 180 mayalso include the element management subsystem (EMS) and a servicemanagement subsystem for the operational support system (OSS).

The connection between GS-E 182 and GS-C 180 may be made over SIP orother protocols. This configuration may enable cellular network system110 to have a central point of control for interacting with multipleenterprises, and may not require the use of SS7 messaging to theenterprise. Rather, it is possible to have a secure IP connectionsupporting SIP. This is also useful for offering a Centrex solution forinterconnecting with a carrier-hosted PBX, or for interconnecting acarrier-hosted gateway server with enterprise-hosted PBX 158 systems.GS-C 180 may support an SS7 point code multiplexer in which only one ortwo point codes are needed to address all enterprises since GS-C 180 canidentify for which enterprise the message is intended. In theillustrative example, GS-C 180 has a point code “Point Code_(A)” andsoftswitch media gateway 181 has a point code “Point Code_(B)”.Originating and terminating triggers used in cellular network system 110for routing calls to GS-C 180 can add identifying information of thespecific enterprise in the triggering messages. Alternatively, GS-C 180may identify the enterprise based on the calling party information.

In the illustrative examples provided herein, three mobile terminal (MT)users (illustratively designated “John Doe_1”-“John Doe_3”) are membersof enterprise network 150 and are assigned respective mobile terminals140-142. MT 140 is assigned a MSISDN of 1-214-555-1212, MT 141 isassigned an MSISDN of 1-214-555-1213, and MT 142 is assigned an MSISDNof 1-214-555-1214.

GS-E 182 may include or interface with an Enterprise member database 192that stores records or profiles that define services for members ofenterprise network 150. Enterprise member database 192 may include arecord allocated for enterprise members that have mobiletelecommunication services managed by GS-E 182. In the present example,records 192 a-192 c respectively associate a subscriber or member namewith an MSISDN of the member's mobile terminal.

The enterprise may maintain a member schedule database 194 thatmaintains schedules of enterprise members. The schedules may includedaily, weekly, or other scheduling blocks that specify where aparticular member is scheduled to be located. For example, if theenterprise comprises an education facility such as a college, theenterprise members in this instance may comprise students and faculty.Accordingly, member schedule database 194 may maintain schedules ofstudents and faculty that specify times at which members are scheduledto be at a particular location, e.g., in a particular class held in aspecific building and room.

In an embodiment, GS-E 182 may interface with schedule database 194,e.g., via an application programming interface (API), for issuingqueries to determine members' scheduled locations. Queries of scheduledatabase 194 may, for example, be issued from an administrator clientsystem 196. Commands for disabling particular telecommunication servicesof members may also be issued from administrator client system 196,e.g., in the event of an emergency, as described more fully hereinbelow.

FIG. 2 is a diagrammatic representation of an embodiment of GS-C 180depicted in FIG. 1. GS-C 180 includes hardware and an operating system210, such as an instance of the Unix operating system. Various protocolstacks may be deployed and run by the gateway server. In theillustrative example, the gateway server includes a network layer 220,such as an Internet Protocol layer. Transport layer(s), such as userdatagram protocol (UDP) 222, transport control protocol (TCP) layer 224,and stream control transmission protocol (SCTP) layer 226, may beincluded in the gateway server and interface with the lower networklayer 220 and applications above the transport layer. Application layersthat interface with lower transport layers may include a sessioninitiation protocol (SIP) layer 228 for creating, modifying, andterminating sessions with one or more devices and H.323 compliant layer230 for provisioning of communication sessions over a packet network.The gateway server additionally includes mobile networking protocollayers, such as ANSI-41 and GSM layers 232. Advanced intelligent networkand wireless intelligent network capabilities may be provided by thegateway server via, for example, a Customized Applications for Mobilenetworks Enhanced Logic (CAMEL) layer 234 and/or a wireless intelligentnetwork (WIN) layer that allows an operator to define services over andabove standard services provided by the GSM standards. The gatewayserver may include any variety of applications, such as H.323communication application 240, an element management subsystem 242, ashort message service system 244, BGW 246, and an applicationprogramming interface 248. Additionally, the gateway server may includea session initiation protocol layer 250, gateway GPRS support node homeagent application 252, gateway mobile services switching center 254,session control protocol 256, and home location register/home subscriberserver application 258. Various other applications may be included inaddition to, or in lieu of, any one or more of the depictedapplications.

The gateway server enables the enterprise to manage and control itscellular service in addition to providing a significant overall costreduction for telecommunications. Moreover, the gateway server includesan overall platform and architecture for improved and integratedwireless enterprise solutions and facilitates convergence between theenterprise's cellular and Voice over IP (Internet Protocol)infrastructure.

The gateway server leverages the benefits of Voice over IP with cellularto extend the cellular network into the enterprise. The gateway serveraddresses both cellular voice and data, and is a networking solutionthat works together with the enterprise's existing PBX, performingmobile session control functions (routing and services) for voice anddata.

Additionally, the gateway server bridges the enterprise PBX and publiccellular environments to enable telecom applications for the cellularuser, such as short-code dialing (e.g. 4 and 5-digit dialing), onenumber service (one phone number for the land-line and cellular phone),and single voice mail box that services both a user's land-line andcellular telephone. The gateway server enables the enterprise toleverage existing telecom assets for cellular use (e.g., least-costrouting over a corporation's VoIP or leased-lines network for discountedlong distance, use of existing PBX voicemail system, etc.).

The gateway server is an application platform for deploying mobile ITapplications. Either the enterprise IT department or a SystemsIntegrator may develop and integrate specific applications to interfacewith the corporation's cellular devices. For example, the enterprise canchoose to replace the desk phone of an enterprise member with aninexpensive mobile phone. For this member, when they ‘badge-out’ of thebuilding at the end of the day, the enterprise security system can beused to inform the gateway server to de-activate the mobile phone, untilthe member returns and ‘badges-in’ the next morning. Alternatively, thegateway server can track and record calls made outside the office hours,and enable the enterprise to charge them to the business, to theemployee, or record them as an enterprise benefit.

The gateway server may be a software-only solution that can execute onstandard, inexpensive Linux platforms. The gateway server may comprise amobile core network (for call handling and routing) and services network(voice and data services such as PBX-based short code dialing,voicemail, conference calling, VPN, etc.) components. It may beappropriately scaled down to the smaller subscriber base of adecentralized large enterprise, in the order of hundreds to severalthousand subscribers, compared with carrier systems that manage manymillions of “centralized” subscribers. The gateway server is designed tobe managed and maintained by the same IT group that currently managesthe enterprise's PBX system.

FIG. 3 is a diagrammatic representation of enterprise facility 300 inwhich schedule-based telecommunication policies may be enforced inaccordance with an embodiment. Facility 300 may comprise any number ofbuildings 310-316 illustratively designated “Building_1”-“Building_4”.Enterprise facility 300 may comprise, for example, an educationalfacility, such as a university or high school, a corporate facility, orother organization entity that may have members associated therewith.

In the illustrative example, assume enterprise facility 300 is locatedin a geographic area of a cell site 320 provisioned by a BTS 134 ofcellular network system 110 depicted in FIG. 1. Further assumeenterprise network 150 depicted and described in FIG. 1 is deployed infacility 300 and is interconnected with cellular network system 110. Inan embodiment, schedule-based communication service policies areenforced on enterprise member mobile terminals as described more fullyhereinbelow.

FIG. 4 diagrammatic representation of an embodiment of a scheduledatabase 194 configured for enterprise member schedules. In theillustrative example, database 194 comprises a table comprising aplurality of records 410 a-410 c (collectively referred to as records410) and fields 420 a-420 h (collectively referred to as fields 420)although other data structures may suitably be substituted therefore.Database 194 may be stored on a disk drive or other storage device,fetched therefrom, and processed by a data processing system, such as aprocessor of GS-E 182.

Fields 420 a-420 h have a respective label, or identifier, thatfacilitates insertion, deletion, querying, or other data operations ormanipulations of database 194. In the illustrative example, fields 420a-420 h have respective labels of “Member”, “Schedule_1”, “Location_1”,“Schedule_2”, “Location_2”, “Exception_1,” “Exception_2”, and “Suspend”.

The Member field 420 a includes data elements that specify an enterprisemember, e.g., a first and last name. Field 420 b specifies a scheduletime during which a member of a corresponding record 410 a-410 c isscheduled to be in a location specified by corresponding Location field420 c. Thus, for example, the member “John Doe_1” is scheduled to belocated in building 310 (“Building_1”) in a room designated “Room_104”from 8:00-8:50. In a similar manner, schedule field 420 d specifies ascheduled time during which a member is scheduled to be located in alocation specified by corresponding location field 420 e.

In accordance with an embodiment, GS-E 182 may be configured to prohibitcommunication services to mobile terminals of members according to themembers' schedules. For instance, in an embodiment, voice and dataservices may be prohibited from originating from, or terminating to, amobile device of a member when the member is scheduled to be in aparticular enterprise location. Thus, for example, GS-E 182 may prohibitvoice and data sessions from or to mobile terminal 140 assigned to “JohnDoe_1” from 8:00-8:50 and 9:00-9:50. Assume, for example, that anattempt to place a call from mobile terminal 140 is made at 8:10. Thecall request is first routed to GS-C 180, which is configured torecognize mobile terminal 140 as assigned to a member of enterprisenetwork 150. Accordingly, the call request is routed to GS-E 182 fromGS-C 180 for call processing. When the call attempt is received by GS-E182, GS-E 182 may identify “John Doe_1” as the member assigned to mobileterminal 140, e.g., via interrogation of member database 192. GS-E 182may then interrogate schedule database 194 to identify the schedule ofthe member associated with mobile terminal 140. In this instance, record410 a, or a portion thereof, may be returned to GS-E 182. A comparisonof the current time as maintained by GS-E 182 with the schedule resultsin a determination that the member currently has a scheduled location.Accordingly, GS-E 182 may then transmit a failure notification to GS-C180, which in turn may notify MT 140, and the call attempt is thenterminated or other suitable treatment such as playing a recordingindicating that this call cannot proceed at this time. In a similarmanner, an incoming call placed to MT 140 when the member assigned to MT140 is scheduled to be in an enterprise location results in routing ofthe call from GS-C 180 to GS-E 182 for call processing instructions. Onreceipt of the inbound call setup request, GS-E 182 determines thecalled member is scheduled to be in an enterprise location, and may thenprovide a call rejection notification to the GS-C 180. GS-C 180 may, inturn, notify the calling party that the call has been rejected.Alternatively, GS-C 180 may terminate the call with a voice mail system.

In accordance with another embodiment, exceptions to the schedule-basedpolicy enforcement may be allowed by specifying numbers to which callsmay be originated or from which calls may be received. For example, ifGS-E 182 is deployed in a high school, students may be prohibited fromreceiving calls or placing calls during scheduled class periods, but mayhave exemptions to allow placement and reception of calls fromparticular individuals, such as the students' parents, school principal,or other person or entity designated as an exception. To this end,schedule database 194 may specify exceptions that define phone numbersthat students may receive calls from and/or place calls to. In theillustrative example, fields 420 f-420 g specify exceptions comprisingphone numbers that are to be allowed to be terminated with a member'smobile terminal regardless of whether the member is scheduled to be inan enterprise location when the call is placed or received.

FIG. 5 is a flowchart 500 depicting a schedule-based communicationspolicy enforcement routine implemented in accordance with an embodiment.The policy enforcement routine may be implemented on a computer-readablemedium as computer-executable instructions that are fetched from aprocessing system, such as GS-E 182, and processed thereby.

The policy enforcement routine is invoked (step 502), for example onreceipt of an outbound or inbound call request (step 504), i.e., a callplaced by an enterprise member or a call directed to an enterprisemember. The telephone number of the call request may then be used tointerrogate member database 192 to determine the member's name (step506). Schedule database 194 may then be queried with the member's name(step 508). GS-E 182 may then evaluate whether a schedule was receivedfrom member database 194 (step 510). In the event that a schedule is notreturned responsive to the schedule database query, GS-E 182 may thencomplete the call setup (step 512), and the policy enforcement routinecycle may then end (step 518).

Returning again to step 510, in the event that a schedule is returned,GS-E 182 may then evaluate the schedule to determine if the member iscurrently scheduled to be in an enterprise location (step 514). Forexample, GS-E 182 may compare a clock maintained thereby or interfacedtherewith with schedule fields of the returned schedule. If the memberis not scheduled to be in an enterprise location, GS-E 182 may completethe call setup according to step 512. If the member is currentlyscheduled to be in an enterprise location, GS-E 182 may proceed toperform a location check to evaluate if the member is currently locatedat the scheduled location (step 515). The location check may beimplemented as a subroutine for evaluating a member's current locationas described more fully hereinbelow with reference to FIG. 9. If it isdetermined that the member is located at the scheduled location, theGS-E 182 may then reject the call (step 516), and the policy enforcementroutine cycle may then end according to step 518. If it is determinedthat the member is not currently located at the scheduled location, GS-E182 may complete the call setup according to step 512.

In an alternative embodiment, a call may be allowed within a predefinedtime period, e.g., 3 minutes, when a member is scheduled to be at anenterprise location. For example, assume GS-E 182 is configured to allowa call to or from a member MT if the call is placed within a memberscheduled time period for up to 3 minutes. In this instance, a callplaced by MT 140 at 8:00 may be allowed, but a call placed any timebetween 8:03 and 8:47 would be rejected.

In accordance with another embodiment, a schedule-based communicationspolicy enforcement routine may restrict communication capabilities basedon both a member schedule and location. For example, particularenterprise locations may have a communication restriction policyassigned thereto, while other enterprise locations do not have such arestriction policy.

FIG. 6 is a flowchart 600 depicting processing of a schedule andlocation-based communications policy enforcement routine for restrictingcommunication service privileges based on a member schedule andlocation. The policy enforcement routine of FIG. 6 may be implemented ona computer-readable medium as computer-executable instructions that arefetched from a processing system, such as GS-E 182, and processedthereby.

The policy enforcement routine is invoked (step 602), for example onreceipt of an outbound or inbound call request (step 604), i.e., a callplaced by an enterprise member or a call directed to an enterprisemember. The telephone number of the call request may then be used tointerrogate member database 192 to determine the member's name (step606). Schedule database 194 may then be queried with the member's name(step 608). GS-E 182 may then evaluate whether a schedule was receivedfrom member database 194 (step 610). In the event that a schedule is notreturned responsive to the schedule database query, GS-E 182 may thencomplete the call setup (step 612), and the policy enforcement routinecycle may then end (step 620).

Returning again to step 610, in the event that a schedule is returned,GS-E 182 may then evaluate the schedule to determine if the member iscurrently scheduled to be in an enterprise location (step 614). Forexample, GS-E 182 may compare a clock maintained thereby or interfacedtherewith with schedule fields of the returned schedule. If the memberis not scheduled to be in an enterprise location, GS-E 182 may completethe call setup according to step 612. If the member is currentlyscheduled to be in an enterprise location, GS-E 182 may then evaluatethe enterprise location at which the member is scheduled to be locatedto determine if the location is prohibited from communication services(step 616). In the event that the enterprise location at which themember is scheduled to be located is not designated as prohibited forcommunication services, setup of the call may then be completedaccording to step 612. If the location at which the member is scheduledto be located is designated as prohibited from communication services,GS-E 182 may proceed to perform a location check to evaluate if themember is currently located at the scheduled location (step 617). Thelocation check may be implemented as a subroutine for evaluating amember's current location as described more fully hereinbelow withreference to FIG. 9. If it is determined that the member is notcurrently located at the scheduled location, GS-E 182 may then completethe call setup according to step 612, and the policy enforcement routinecycle may then end according to step 620. If it is determined that themember is located at the scheduled location, the GS-E 182 may thenreject the call (step 618), and the policy enforcement routine cycle maythen end according to step 620.

In accordance with another embodiment, exceptions or exemptions to theschedule-based policy enforcement may be allowed by specifying numbersto which calls may be originated or from which calls may be received. Inthis manner, members may be prohibited from receiving calls or placingcalls during scheduled class periods, but may have exemptions to allowplacement and reception of calls from particular individuals regardlessof whether the member is scheduled to be in an enterprise location whenthe call is placed or received.

FIG. 7 is a flowchart 700 depicting a schedule-based communicationspolicy enforcement routine that facilitates service restrictionexemptions implemented in accordance with an embodiment. The policyenforcement routine of FIG. 7 may be implemented on a computer-readablemedium as computer-executable instructions that are fetched from aprocessing system, such as GS-E 182, and processed thereby.

The policy enforcement routine is invoked (step 702), for example onreceipt of an outbound or inbound call request (step 704), i.e., a callplaced by an enterprise member or a call directed to an enterprisemember. The telephone number of the call request may then be used tointerrogate member database 192 to determine the member's name (step706). GS-E 182 may then evaluate the destination or called number in theevent the call is originated from an enterprise member, or alternativelyevaluate the origination number in the event the call was placed to anenterprise member, to determine if the called or calling party isdesignated as an exemption for the member (step 707). If the phonenumber is identified as an exemption, GS-E 182 may then proceed tocomplete the call setup (step 712). If the phone number is not evaluatedas an exemption, GS-E 182 may then query schedule database 194 with themember's name (step 708). GS-E 182 may then evaluate whether a schedulewas received from member database 194 (step 710). In the event that aschedule is not returned responsive to the schedule database query, GS-E182 may then complete the call setup according to step 712, and thepolicy enforcement routine cycle may then end (step 720).

Returning again to step 710, in the event that a schedule is returned,GS-E 182 may then evaluate the schedule to determine if the member iscurrently scheduled to be in an enterprise location (step 714). Forexample, GS-E 182 may compare a clock maintained thereby or interfacedtherewith with schedule fields of the returned schedule. If the memberis not scheduled to be in an enterprise location, GS-E 182 may completethe call setup according to step 712. If the member is currentlyscheduled to be in an enterprise location, the GS-E may then proceed toperform a location check to evaluate if the member is currently locatedat the scheduled location (step 716). The location check may beimplemented as a subroutine for evaluating a member's current locationas described more fully hereinbelow with reference to FIG. 9. If it isdetermined that the member is not currently located at the scheduledlocation, GS-E 182 may then complete the call setup according to step712, and the policy enforcement routine cycle may then end according tostep 720. If it is determined that the member is located at thescheduled location, the GS-E 182 may then reject the call (step 718),and the policy enforcement routine cycle may then end according to step720.

In accordance with another embodiment, an enterprise administrator maybe authorized to suspend the scheduled-based service prohibition ofmembers based on the members' locations. For example, an administratorat system 196 may perform a query for all members scheduled to belocated at a particular enterprise location, or alternatively allmembers scheduled to be located at any enterprise location excluding aparticular location. Any members having a scheduled location thatmatches the enterprise administrators query may then have theircommunication services restriction suspended thereby allowing theenterprise member to utilize their telecommunication services. Such anenterprise system feature may be advantageous in an emergency scenario.For example, in the event that an emergency, such as a shooting or otherdisaster, occurs that effects one of numerous enterprise facilities,such as a particular building, it may be desirable for communicationservices to be disabled for members that are not scheduled to be locatedat the building experiencing the emergency. In this manner, overloadingof the communication system capacity may be avoided by prohibitingenterprise members that are not directly impacted by the emergency fromplacing or receiving calls while allowing members that may be directlyimpacted to place and receive calls. Notably, such a mechanism may proveparticularly advantageous from an emergency response team perspective,e.g., a police or fire department, by allowing the emergency responseteam to place or receive calls to enterprise members effected by theemergency and that have firsthand knowledge of the emergency. To thisend, schedule database 194 may include Suspend field 420 h that containsa value, such as a Boolean True (T) or False (F), that indicates whetherschedule-based communications service restrictions for the particularuser are currently suspended. The Suspend field 420 h value may be setby an authorized enterprise administrator based on members' scheduledlocations in accordance with an embodiment.

During such an event, the administrator can instruct the GS-E toselectively send a SMS message to those members who have had theirservices disabled indicating their services have been temporarilydisabled along with instructions to evacuate the campus. The GS-E wouldensure the SMS messages will bypass the service restrictions in order tobe delivered.

FIG. 8 is a flowchart 800 depicting a schedule-based communicationspolicy enforcement routine including emergency service restrictionsuspension implemented in accordance with an embodiment. The policyenforcement routine of FIG. 8 may be implemented on a computer-readablemedium as computer-executable instructions that are fetched from aprocessing system, such as GS-E 182, and processed thereby.

The policy enforcement routine is invoked (step 802), for example onreceipt of an outbound or inbound call request (step 804), i.e., a callplaced by an enterprise member or a call directed to an enterprisemember. The telephone number of the call request may then be used tointerrogate member database 192 to determine the member's name (step806). GS-E 182 may evaluate the member's scheduled location to determineif the service restriction has been suspended (step 807), e.g., foremergency purposes. In this instance, GS-E 182 may read the Suspendfield 420 h value to determine if the service restriction has beensuspended. If the service restriction has been suspended, GS-E 182 maythen allow the call setup to be completed (step 812). If the servicerestriction has not been suspended, GS-E 182 may then query scheduledatabase 194 with the member's name (step 808). GS-E 182 may thenevaluate whether a schedule was received from member database 194 (step710). In the event that a scheduled is not returned responsive to theschedule database query, GS-E 182 may then complete the call setup (step812), and the policy enforcement routine cycle may then end (step 820).

Returning again to step 810, in the event that a schedule is returned,GS-E 182 may then evaluate the schedule to determine if the member iscurrently scheduled to be in an enterprise location (step 814). Forexample, GS-E 182 may compare a clock maintained thereby or interfacedtherewith with schedule fields of the returned schedule. If the memberis not scheduled to be in an enterprise location, GS-E 182 may completethe call setup according to step 812. If the member is currentlyscheduled to be in an enterprise location, GS-E 182 may then proceed toperform a location check to evaluate if the member is currently locatedat the scheduled location (step 816). The location check may beimplemented as a subroutine for evaluating a member's current locationas described more fully hereinbelow with reference to FIG. 9. If it isdetermined that the member is not located at the scheduled location, theGS-E 182 may then complete the call according to step 812, and thepolicy enforcement routine cycle may then end according to step 820. Ifit is determined that the member is currently located at the scheduledlocation, GS-E 182 may then reject the call (step 818), and the policyenforcement routine cycle may then end according to step 820.

As an example, consider the members assigned to MTs 140-141 depicted inFIG. 1. Assume the members are located on enterprise facility 300 at thetime 8:30. In this instance, both members assigned to MTs 140 and 141are scheduled to be in respective building 310 (“Building 1”) andbuilding 312 (“Building 2”) according to records 410 a and 410 b ofschedule database 194. Accordingly, under normal, non-emergency or othercommunication service scheduled-based restrictions, neither MT 140-141would be allowed to place or receive a call from anyone other than adesignated exemption. Assume that an emergency has occurred in building312 (Building 2), and that an enterprise administrator has supplied aservice restriction suspension for any members located in building 312as designed by the restriction suspension value (T) in record 410 b. Nowassume a call is originated from MT 141. Accordingly, in this instance,although the member assigned to MT 141 is currently scheduled to belocated in an enterprise location, the call will be allowed according tothe service restriction suspension evaluation at step 816.

Suspension of schedule-based service restrictions may be provided on anyphysical resolution allocated in schedule database 194. For example, ifan emergency is determined to be isolated to a particular room, servicerestriction may be suspended only for members scheduled to be in aparticular room, while other members scheduled to be in the samebuilding where the emergency has occurred may still have their servicerestriction active. The geographic resolution of the service restrictionmay be determined and set in schedule database 192 according to theenterprise administrator's judgment.

In various instances, an enterprise member may be scheduled to be at aparticular location but, for any number of reasons (e.g., they are homesick, traveling to another location, etc.), may not actually be locatedat the scheduled location. In these instances, it is desirable to notenforce policy restrictions based on the member's scheduled location.

FIG. 9 is a flowchart 900 depicting a location evaluation subroutineimplemented in accordance with an embodiment. The location evaluationsubroutine of FIG. 9 may be implemented on a computer-readable medium ascomputer-executable instructions that are fetched from a processingsystem, such as GS-E 182, and processed thereby. The processing steps ofFIG. 9 generally correspond to steps 515, 617, 716, and 816 of FIGS.5-8.

The location evaluation subroutine is invoked (step 902), and GS-E 182may issue a request for MSC and/or BSC location area information andreceive the location information (step 904). The location request may,for example, be issued to GS-C 180 that may interrogate one or moremobile network 110 entities. MSC-level location information providesvery general information, such as a general location within ametropolitan area, while BSC-level location provides more detailedinformation, such as specifying a location within 1 mile of a particulargeographic location, such as a highway intersection. GS-E 182 may thenevaluate the location information to determine if the MSC locationinformation corresponds to the scheduled location (step 906). If the MSClocation information does not correspond to the scheduled location, anindication that the member is not at the scheduled location may beprovided by the location evaluation subroutine (step 908) therebyallowing the call setup to complete, and the location evaluationsubroutine cycle may then end (step 918).

Returning again to step 906, if the MSC location area information isdetermined to correspond to the scheduled information, an evaluation maythen be made to determine if the BSC location area informationcorresponds to the scheduled location (step 910). If the BSC locationinformation does not correspond to the scheduled location, an indicationthat the member is not at the scheduled location may be provided by thelocation evaluation subroutine according to step 908. If the BSClocation information is determined to correspond to the scheduledlocation, GS-E 182 may optionally issue a request to GS-C 180 for MLClocation area information and receive MLC information therefrom (step912). MLC location area information may specify global positioningsystem (GPS) information, such as a current latitude and longitude. Thelocation evaluation subroutine may then perform an evaluation todetermine if the MLC location information differs from the scheduledlocation by a predefined distance (step 914). If the MLC locationdiffers from the scheduled location by the predefined distance, thelocation evaluation subroutine may provide an indication that the memberis not at the scheduled location according to step 908. If the MLClocation does not differ from the scheduled location by at least thepredefined distance, the location evaluation subroutine may then providean indication that the member is at the scheduled location (step 916)thereby allowing the service policy restrictions to be enforced, and thelocation evaluation subroutine cycle may then end according to step 918.

As described, embodiments disclosed herein provide mechanisms forenforcing user telecommunication privileges on a per-schedule basis.Enterprise members may have a schedule associated therewith that definesscheduled locations of the users. Telecommunication service privilegesmay be coordinated with the users' schedules such that communicationservices are disabled at particular times based on the users' schedules.In other implementations, particular users may have telecommunicationservices disabled by an administrator in the event of a catastrophe oremergency. By this mechanism, users that are not proximate to aparticular catastrophe or emergency area according to the users'schedule may have services disabled while other users that are locatedmore proximate to the emergency may have their telecommunicationservices enabled. In this manner, the demand on a cellular network maybe alleviated thereby increasing the likelihood that users directlyimpacted by the emergency may receive and place calls or access dataservices.

While the disclosed embodiments have been described with reference toprohibiting mobile calls according to enterprise member schedules, itshould be apparent that enforcing data services, such as mobile Internetaccess, short message service (SMS), or other data services, maysimilarly be implemented in accordance with the described embodiments.The descriptions provided herein related to schedule-based restrictionsof voice calls is exemplary only and are provided only to facilitate anunderstanding of the disclosed embodiments.

Although the specific network architecture and nomenclature are depictedand described according to the GSM, it is understood that this is doneso for illustrative purposes only and that the network architecture onwhich embodiments disclosed herein may be applied is not limited to anyparticular standard, but rather may be equivalently implemented on anyother communications system supporting any variety of cellularcommunication systems, e.g. D-AMPS, GSM, CDMA, IS-41, ANSI-41, UMTS,WiFi, WiMAX, LTE, etc.

The flowcharts of FIGS. 5-9 depict process serialization to facilitatean understanding of disclosed embodiments and are not necessarilyindicative of the serialization of the operations being performed. Invarious embodiments, the processing steps described in FIGS. 5-9 may beperformed in varying order, and one or more depicted steps may beperformed in parallel with other steps. Additionally, execution of someprocessing steps of FIGS. 5-9 may be excluded without departing fromembodiments disclosed herein.

The illustrative block diagrams and flowcharts depict process steps orblocks that may represent modules, segments, or portions of code thatinclude one or more executable instructions for implementing specificlogical functions or steps in the process. Although the particularexamples illustrate specific process steps or procedures, manyalternative implementations are possible and may be made by simpledesign choice. Some process steps may be executed in different orderfrom the specific description herein based on, for example,considerations of function, purpose, conformance to standard, legacystructure, user interface design, and the like.

Aspects of the present invention may be implemented in software,hardware, firmware, or a combination thereof. The various elements ofthe system, either individually or in combination, may be implemented asa computer program product tangibly embodied in a machine-readablestorage device for execution by a processing unit. Various steps ofembodiments of the invention may be performed by a computer processorexecuting a program tangibly embodied on a computer-readable medium toperform functions by operating on input and generating output. Thecomputer-readable medium may be, for example, a memory, a transportablemedium such as a compact disk, a floppy disk, or a diskette, such that acomputer program embodying the aspects of the present invention can beloaded onto a computer. The computer program is not limited to anyparticular embodiment, and may, for example, be implemented in anoperating system, application program, foreground or background process,driver, network stack, or any combination thereof, executing on a singlecomputer processor or multiple computer processors. Additionally,various steps of embodiments of the invention may provide one or moredata structures generated, produced, received, or otherwise implementedon a computer-readable medium, such as a memory.

Although embodiments of the present disclosure have been described indetail, those skilled in the art should understand that they may makevarious changes, substitutions and alterations herein without departingfrom the spirit and scope of the present disclosure.

What is claimed is:
 1. A method, comprising: receiving a communicationssession setup request at a carrier gateway server; routing thecommunications session setup request to an enterprise gateway server;obtaining a schedule of a member that specifies at least one scheduledlocation of the member via a schedule database; performing a comparisonof the schedule with a current time at which the session setup requestis received; determining the member is scheduled to be at the scheduledlocation at the current time; processing the session according to apolicy associated with the scheduled location at the current time;wherein processing the session includes one of completing, rejecting andredirecting the session setup; and transmitting the session processingto the carrier gateway server.
 2. The method of claim 1, wherein themember is an enterprise member.
 3. The method of claim 1, whereinperforming a comparison results in determining a mobile terminal islocated within a predefined distance of the scheduled location.
 4. Themethod of claim 1, wherein performing a comparison results indetermining the member is not scheduled to be at an enterprise locationat the current time.
 5. The method of claim 1, wherein performing acomparison results in determining the member is scheduled to be at anenterprise location, the method further comprising determining whetherone of a session originator and a session destination comprises anexempted party.
 6. The method of claim 5, wherein one of the sessionoriginator and the session destination is determined to comprise anexempted party.
 7. The method of claim 5, wherein neither of the sessionoriginator and the session destination is determined to comprise anexempted party.
 8. The method of claim 1, further comprising suspendinga service restriction of a mobile terminal based on a determination thatthe member is located within a predefined distance of a scheduledlocation.
 9. A non-transitory computer-readable medium havingcomputer-executable instructions for execution by a processing system,the computer-executable instructions comprising: instructions thatreceive a communications session setup request at a carrier gatewayserver; instructions that route the communications session setup requestto an enterprise gateway server; instructions that obtain a schedule ofa member that specifies at least one scheduled location of the membervia a schedule database; instructions that perform a comparison of theschedule with a current time at which the session setup request isreceived; instructions that determine the member is scheduled to be atthe scheduled location at the current time; instructions that processthe session according to a policy associated with the scheduled locationat the current time, wherein processing of the session includes one ofcompleting, rejecting and redirecting the session setup; andinstructions that transmit the session process to the carrier gatewayserver.
 10. The non-transitory computer-readable medium of claim 9,wherein the instructions that perform a comparison result in determiningthe member is scheduled to be at a scheduled location at the currenttime, wherein the instructions that process the session perform at leastone of allowing and rejecting data services associated with the mobileterminal.
 11. The non-transitory computer-readable medium of claim 9,wherein the instructions that perform a comparison determine the memberis not scheduled to be at a scheduled location at the current time. 12.The non-transitory computer-readable medium of claim 9, wherein theinstructions that perform a comparison further determine the member isscheduled to be at a scheduled location, the computer-readable mediumfurther comprising instructions that determine whether one of a sessionoriginator and a session destination comprises an exempted party. 13.The non-transitory computer-readable medium of claim 12, wherein one ofthe session originator and the session destination is determined tocomprise an exempted party.
 14. The non-transitory computer-readablemedium of claim 12, wherein neither of the session originator and thesession destination is determined to comprise an exempted party.
 15. Thenon-transitory computer-readable medium of claim 9, further comprisinginstructions that suspend a service restriction of the mobile terminalbased on a determination that the member is located within a predefineddistance of the scheduled location.
 16. The non-transitorycomputer-readable medium of claim 9, wherein the instructions thatperform a comparison determine the mobile terminal is located within apredefined distance of the scheduled location.
 17. The non-transitorycomputer-readable medium of claim 9, further comprising instructionsthat: identify the mobile terminal as having a service restricted; andtransmit a message to the mobile terminal indicating the service hasbeen restricted.
 18. A system, comprising: a cellular network includinga carrier gateway server; and an enterprise gateway servercommunicatively coupled with the carrier gateway server and adapted tointerface with a schedule database that specifies scheduled locations ofan enterprise member; wherein the cellular network receives a sessionsetup request; wherein the cellular network routes the session setuprequest to the enterprise gateway server; wherein the enterprise gatewayserver obtains a schedule of the member that specifies at least onescheduled location of the member, performs a comparison of the schedulewith a current time at which the session setup request is received,determines the member is scheduled to be at the scheduled location atthe current time and processes the session according to a policyassociated with the scheduled location at the current time; whereinprocessing the session includes one of complete, reject and redirect thesession setup and transmit the session processing to the cellularnetwork.
 19. The system of claim 18, wherein the enterprise gatewayserver determines the enterprise member is scheduled to be located at ascheduled location at the current time.
 20. The system of claim 18,wherein the enterprise gateway server determines the enterprise memberis not scheduled to be at a scheduled location at the current time.